Method for processing requests for location

ABSTRACT

The present invention discloses a method for processing requests for location, which comprises: A target UE sending a request for location to the Location Service (LCS) system and asking the LCS system to provide a requestor with the location information of the target UE; the LCS system positioning the target UE, acquiring the location estimate of the target UE, and deciding whether it is needed to hide the real identity of the target UE, and if yes, the LCS system sending the pseudonym and location information of the target UE to the requestor; otherwise, the LCS system sending the real identity and location information of the target UE to the requestor. The invention makes it possible for the LCS system to decide whether to hide the real identity of the target UE according to the user&#39;s requirement, improving the flexibility of the location service. As the LCS system is able to hide the real identity of the target UE, the security of using the location service is enhanced.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a Continuation Application of InternationalApplication Number PCT/CN2005/000169, filed on Feb. 6, 2005, whichclaims priority of Chinese Patent Application Number 200410004916.0,filed on Feb. 11, 2004.

FIELD OF THE TECHNOLOGY

The present invention relates to positioning techniques for networkequipment, and more particularly, to a method for processing requestsfor location.

BACKGROUND OF THE INVENTION

The location service (LCS) of a mobile communications network is toobtain the location of a target user's equipment (UE) with locationtechniques, wherein the target UE refers to a user terminal which is tobe positioned in a mobile communications network and the location may begeographical information expressed in latitude and longitude or locationdata with reference to local streets. The location obtained by a mobilecommunications network may be offered to the target UE for the targetUE's self-locating, or to the communications network itself forarea-specific charging or operational maintenance, or to otherapplication clients, for instance, agencies or individual, requestingthe location of the target UE for value-added services. Therefore, thelocation service has wide applications in such fields as emergencyrescue, vehicle navigation and intelligent traffic systems, job dispatchand team management, mobile-yellow-page query, and enhancement ofnetwork performance. In the 3^(rd) Generation Partner Project (3GPP),specifications on LCS as well as the operational mode, structure, statedescription, and message flow for implementing the LCS have beendescribed.

FIG. 1 is a schematic diagram illustrating the logical structure forimplementing the LCS. As shown in FIG. 1, a requestor 101 requests thelocation of a target UE 103 from a network 102 which contains an LCSsystem. The network 102 makes a validity authentication of the requestor101 to check whether the target UE 103 permits providing the location ofthe target UE 103 for the requestor 101. If the requestor 101 passes thevalidity authentication by the network 102, the network 102 will acceptthe request initiated by the requestor 101 for the location of thetarget UE 103, locate the target UE 103, and provide the requestor 101with the positioning result of the target UE 103; otherwise, the network102 will reject the request initiated by the requestor 101 for thelocation of the target UE 103. For the purpose of description, thenetwork containing an LCS system is hereinafter named an LCS system forshort. Here, the request for location originated by the target UE may bea Location Service Invoke sent to a Mobile Switch Center (MSC)/MSCServer or an LCS MO-LR Invoke sent to a Serving General Packet RadioService (GPRS) Support Node (SGSN); the requestor may be an LCS Client,a group of LCS Clients, the target UE itself, or any other terminal thatis able to process the location information of the target UE.

Logical functionality for implementing the location service in an LCSsystem include a Gateway Mobile Location Center (GMLC), a SubscriberData Storage Server, such as a Home Location Register/Home SubscriberServer (HLR/HSS), a Core Network (CN), and a Radio Access Network (RAN).The GMLC may further include a Requesting GMLC (R-GMLC), a Home GMLC(H-GMLC), and a Visited GMLC (V-GMLC). The R-GMLC is the GMLC forreceiving the request for location of the target UE initiated by arequestor, The H-GMLC refers to the GMLC which the target UE belongs to,and the V-GMLC refers to the GMLC which currently serves the target UE,that is, the GMLC which is associated with the serving node of thetarget UE currently. The R-GMLC, the H-GMLC, and the V-GMLC may beintegrated in the same physical entity, or may be in separate physicalentities.

So far, a procedure of a Mobile Originating Location Request (MO-LR) hasbeen defined in the 3GPP specifications. The MO-LR is a requestinitiated by a target UE for its own location from an LCS system. Afterpositioning the target UE, the LCS system will return a positioningresult to the target UE. Furthermore, based on the request of the targetUE, the LCS system may provide the positioning result of the target UEfor an external requestor. The requestor herein refers to an LCS clientor other application client that is able to handle the locationinformation of the target UE.

FIG. 2 is a flowchart for processing an MO-LR in the prior art. As shownin FIG. 2, the processing of an MO-LR comprises the steps of:

Step 201: A target UE sends a service request carrying the identity ofthe target UE to the CN via RAN, requesting to establish a radiosignaling connection with an LCS system. Then the LCS system mayinitiate a procedure of authentication and ciphering for the target UEaccording to the identity of the target UE. If the target UE has beenauthenticated by the network containing the LCS system, continue withstep 202; otherwise, reject the service request for establishing a radiosignaling connection initiated by the target UE and terminate thecurrent processing of the MO-LR.

Steps 202: The target UE sends a Location Service Invoke including anidentity of the target UE to the CN via RAN, requesting the LCS systemto position the target UE and return the positioning result to thetarget UE. The Location Service Invoke may further carry an identity ofa requestor, requesting the LCS system to provide the locationinformation of the target UE for the requestor. The Location ServiceInvoke may further carry a GMLC address designated by the target UE,requesting the CN to provide the location information of the target UEfor the requestor via the GMLC corresponding to the GMLC address. if theLocation Service Invoke carries no GMLC address, The CN will assign aGMLC for the Location Service Invoke according to the assigned GMLCaddress saved in the CN and provide the requestor with the locationinformation of the target UE via the GMLC assigned by the CN. Wherein,the GMLC assigned by the CN is called V-GMLC.

Steps 203˜205: After receiving the Location Service Invoke, the CN sendsa Location Request carrying the identity of the target UE to the RAN.Upon receiving the Location Request, the RAN will position the target UEaccording to the identity of the target UE. If the RAN succeeds inpositioning the target UE, it returns a Location Report including thelocation information of the target UE to the CN. After the CN receivesthe Location Report carrying the location information of the target UE,it determines whether the Location Service Invoke initiated by thetarget UE carries a GMLC address or not, and if yes, The CN willcontinue to decide whether the CN itself can directly access the GMLCwhich corresponds with the GMLC address. If the CN can directly accessthe GMLC, it will send a Subscriber Location Report of the target UEdirectly which carries the identity and location information of thetarget UE to the GMLC. Wherein the interaction between the V-GMLC andthe GMLC as shown in FIG. 2, i.e., Steps 207 and 210, may be skipped; ifthe CN can not access the GMLC directly, it will assign a V-GMLC thatcan directly be accessed by itself, and send a Subscriber LocationReport to the V-GMLC which includes the identity and locationinformation of the target UE, the identity of the requestor, and theGMLC address carried in the Location Service Invoke, and then continuewith Step 206. If the Location Service Invoke initiated by the target UEcarries no GMLC address, the CN will assign a V-GMLC that can bedirectly accessed by the CN, send a Subscriber Location Report of thetarget UE to the V-GMLC which carries the target UE's identity, thelocation information of the target UE, and the requestor's identity, andthen continue with Step 206. If the RAN fails to position the target UE,it will return a Location Report carrying a value of error cause to theCN, and go directly to Step 212, i.e., the CN sends an LCS MO-LR ReturnResult carrying the value of error causes to the target UE via RAN.

Step 206: After receiving the Location Report of the target UE, theV-GMLC decides whether it carries the address of the GMLC, and if itdoes, then go to Step 207; otherwise, the V-GMLC will determine whetherit is able to access the requestor directly according to the identity ofthe requestor. If the V-GMLC can access the director directly, it willdirectly send a Location Information of the target UE which carries theidentity and location information of the target UE to the requestor,wherein the interaction between the V-GMLC and the GMLC, i.e., Step 207and Step 210, may be skipped; otherwise, the V-GMLC will assign a GMLCthat can access the requestor according to the identity of therequestor, and then continue with Step 207.

Step 207: Based on the GMLC address, the V-GMLC sends an MO-LR LocationInformation which carries the identity of the target UE, the locationinformation of the target UE, and the identity of the requestor to theGMLC. In LCS, an MO-LR Location Information sent to a GMLC, a MobileApplication Part (MAP) Subscriber Location Report or Subscriber LocationReport sent to a V-GMLC, a Location Information sent to the requestormay be called a location report of the target UE in a generaldesignation.

Step 208: After receiving the MO-LR Location Information of the targetUE, the GMLC sends a Location Information of the target UE which carriesthe identity and location information of the target UE to the requestoraccording to the identity of the requestor.

Step 209: After receiving the Location Information of the target UE,according to the service requirement, the requestor makes acorresponding process of the target UE's location information and thenreturns a Location Information Ack of the target UE to the GMLC. If theLocation Information of the target UE received by the requestor is fromthe V-GMLC, the requestor will directly return the Location InformationAck of the target UE to the V-GMLC.

Step 210: Upon receiving the Location Information Ack of the target UE,the GMLC returns an MO-LR Location Information Ack of the target UE tothe V-GMLC. If the MO-LR Location Information received by the GMLC comesfrom the CN, the GMLC directly returns the CN a Subscriber LocationReport Ack of the target UE.

Step 211: After receiving the MO-LR Location Information Ack of thetarget UE, the V-GMLC returns the CN a Subscriber Location Report Ack ofthe target UE.

Step 212: After receiving the Subscriber Location Report Ack, the CNsends the target UE an LCS MO-LR Return Result carrying the locationinformation of the target UE via RAN, which informs the target UE thatits location information has been provided for the appropriate requestorand notifies the target UE the processing result of the target UE'slocation information for the requestor.

If the requestor is able to process the location information of thetarget UE based on the service requirement, the Location Information Ackof the target UE that the requestor returns to the LCS system willinclude a success flag, and correspondingly, the LCS MO-LR Return Resultwhich the LCS system sends to the target UE will carry a success flagand further include the requestor's process result of the target UE'slocation information; if the requestor cannot process the locationinformation of the target UE according to the service requirement, theLocation Information Ack of the target UE returned by the requestor tothe LCS system will carry a failure flag, and correspondingly, the LCSMO-LR Return Result sent by the LCS system to the target UE will includea failure flag and may further carry a value of error cause. Here, thelocation information is for describing the location of the target UE.The location information transmitted among the entities in network side,e.g., the RAN, GMCL, V-GMLC, and CN, may not be processable forterminals e.g., requestors and UE. So when a network entity sends thelocation information of the target UE to a requestor, the entity mayfirst make a transformation for the received location information. Thusthe received location information is transformed into another form oflocation information which can be processed by the requestor, and theentity can subsequently send the transformed location information to therequestor.

As seen from the MO-LR procedure defined by the 3GPP specifications saidabove, if the target UE requests its own location to an LCS system andasks the LCS system to provide the location information of the target UEfor a requestor, after positioning the target UE and obtaining thelocation estimate of the target UE, the LCS system will provide thelocation information of the target UE for the requestor according to thelocation estimate. As providing the requestor with the locationinformation of the target UE, the LCS system simultaneously provides areal identity of the target UE to the requestor. The real identity is akind of identity that is assigned to the target UE in a unified way bythe mobile communications network and is able to uniquely identify thetarget UE, e.g., the Mobile Station International ISDN Number (MSISDN)or the International Mobile Subscriber Identity (IMSI). In practice,when a target UE requests an LCS system that provides a requestor withthe location information of the target UE, for the sake of security andprivacy, the target UE may hope the real identity of itself beconcealed.

SUMMARY

In view of the above, the object of this invention is to provide amethod for processing requests for location so as to improve theflexibility in users' making use of the LCS.

The technical solution in accordance with this invention is as follows:

A method for processing requests for location, the method comprises:

a target UE sending a request for location to a location service (LCS)system, and asking the LCS system to provide a requestor with thelocation information of the target UE; the LCS system positioning thetarget UE and obtaining the location information of the target UE; theLCS system determining whether the real identity of the target UE shouldbe concealed, if yes, sending the location information and a pseudonymof the target UE to the requestor.

The step of determining whether the real identity of the target UEshould be concealed may comprise: determining whether the request forlocation sent by the target UE carries a pseudonym designated by thetarget UE, if yes, sending the location information and pseudonym of thetarget UE to the requestor; otherwise, sending the requestor the realidentity and location information of the target UE.

The step of determining whether the real identity of the target UEshould be concealed may comprise: determining whether the request forlocation sent by the target UE carries a pseudonym indication, if yes,assigning a pseudonym for the target UE, and then sending the locationinformation and pseudonym of the target UE to the requestor; otherwise,sending the requestor the real identity and location information of thetarget UE.

The step of determining whether the real identity of the target UEshould be concealed may comprise: determining whether the request forlocation sent by the target UE carries a pseudonym designated by thetarget UE, if yes, sending the location information and pseudonym of thetarget UE to the requestor; otherwise, further deciding whether therequest for location sent by the target UE carries a pseudonymindication; if the request for location carries a pseudonym indication,assigning a pseudonym for the target UE, and then sending the locationinformation and pseudonym of the target UE to the requestor; if therequest for location carries no pseudonym indication, sending therequestor the real identity and location information of the target UE.

The step of determining whether the real identity of the target UEshould be concealed may comprise: determining whether the request forlocation sent by the target UE carries a pseudonym indication, if therequest for location carries a pseudonym indication, assigning apseudonym for the target UE, and then sending the location informationand pseudonym of the target UE to the requestor; if the request forlocation carries no pseudonym indication, further deciding whether therequest for location sent by the target UE carries a pseudonymdesignated by the target UE; if the request for location carries apseudonym, sending the location information and pseudonym of the targetUE to the requestor; if the request for location carries no pseudonym,sending the real identity and location information of the target UE tothe requestor.

The step of determining whether the real identity of the target UEshould be concealed may comprise: determining whether the requestor forreceiving the target UE's location information should analyze the realidentity of the target UE, if no, assigning a pseudonym for the targetUE, and then sending the location information and the pseudonym of thetarget UE to the requestor; otherwise, sending the requestor the realidentity and location information of the target UE.

In the above solution, the pseudonym may be assigned by a Home GatewayMobile Location Centre (H-GMLC), a Visited Gateway Mobile LocationCentre (V-GLMC), or a Gateway Mobile Location Centre GMLC which canaccess the requestor in the LCS system; alternatively, the pseudonym maybe assigned by a H-GMLC, a V-GLMC, an entity of the LCS system, or aGMLC which can access the requestor after the H-GMLC, the V-GLMC, theentity of the LCS system, or the GMLC interacts with an entity of theLCS system; the entity of the LCS system may be a Pseudonym MediationDevice (PMD) or H-GMLC.

In accordance with the invention, when a target UE requests the locationof itself to an LCS system and asks the LCS system to provide thelocation information of the target UE for a requestor, after acquiringthe target UE's location estimate, the LCS system will decide whether tohide the real identity of the target UE or not while providing therequestor with the location information of the target UE according tothe target UE's indication, and if yes, the LCS system will send thepseudonym and location information of the target UE to the requestor,otherwise, it will send the requestor the real identity and locationinformation of the target UE, so that the LCS system is able to decidewhether to hide the real identity of the target UE according to thesubscriber's demand, and improve the flexibility of the LCS.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating the logical structure forimplementing the location service;

FIG. 2 is the flowchart for processing an MO-LR in the prior art;

FIG. 3 is the flowchart for processing an MO-LR in accordance with anembodiment of the present invention;

FIG. 4 is the flowchart of another embodiment in accordance with thepresent invention;

FIG. 5 is the flowchart of another embodiment in accordance with thepresent invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention is hereinafter described in detail with referenceto the accompanying drawings.

In accordance with the invention, when the target UE requests itslocation to the LCS system and asks the LCS system to provide arequestor with the location information of the target UE, afteracquiring the location estimate of the target UE, the LCS system decideswhether to hide the real identity of the target UE according to theindication of the target UE while providing the requestor with thelocation information of the target UE, and if yes, the LCS system willsend the requestor a pseudonym of the target UE as providing therequestor with the location information of the target UE, wherein thepseudonym may be set by the target UE, or assigned to the target UE bythe LCS system Otherwise, the LCS system will provide the requestor withthe real identity of the target UE while providing the target UE'slocation information for the requestor.

Pseudonym, an assumed identity of the target UE, is for hiding the realidentity of the target UE from a requestor. The pseudonym may be anenciphered form of the target UE's real identity. For example, if thereal identity of the target UE is enciphered by using the common key ofthe target UE's home network, the enciphered result will be a pseudonymof the target UE. In addition, a pseudonym may directly contain theaddress of network entities related to the pseudonym itself, e.g., theaddress of the Pseudonym Management Device (PMD) for assigning thepseudonym or the H-GMLC's address; and the pseudonym may also containthe address of the PMD or the H-GMLC indirectly. By the derivation ofthe pseudonym, the LCS system can obtain the address of network entitiesrelated to the pseudonym.

FIG. 3 is the flowchart for processing an MO-LR in accordance with thepresent invention. As shown in FIG. 3, an MO-LR procedure comprises thefollowing steps:

Steps 301˜302: A target UE originates a request for location to the LCSsystem, requesting the LCS system to position the target UE and toprovide a requestor with the location information of the target UE. TheLCS system positions the target UE and obtains the location informationof the target UE.

Step 303: The LCS system decides whether the request for locationinitiated by the target UE carries a pseudonym, and if yes, go to Step304; otherwise, go to Step 305.

Step 304: The LCS system uses the pseudonym as an identity of the targetUE, sends the requestor the pseudonym and the target UE's locationinformation, and terminates the current MO-LR procedure.

Step 305: The LCS system decides whether the request for locationinitiated by the target UE carries a pseudonym indication, if yes, go toStep 306; otherwise, go to Step 308.

Steps 306˜307: The LCS system assigns the target UE a pseudonym whichcan identify the target UE, then sends the pseudonym and locationinformation of the target UE to the requestor, and terminates thecurrent MO-LR procedure.

Step 308: The LCS system sends the requestor the location information ofthe target UE which includes the real identity of the target UE.

The above Step 303 and Step 305 may swap, i.e., after positioning thetarget UE and acquiring the location information of the target UE, theLCS system may first perform Step 305, i.e., and then decide whether therequest for location originated by the target UE carries a pseudonymindication. If the request for location carries a pseudonym indication,go to Step 306; and if it carries no pseudonym indication, continue todecide whether the request for location originated by the target UEcarries a pseudonym. If the request for location carries a pseudonym, goto Step 304; otherwise, go to Step 308. On the other hand, the aboveStep 303 and Step 304 may be skipped, i.e., after positioning the targetUE and acquiring the location estimate, the LCS system may perform Step305. That is, the LCS system decides whether the request for locationoriginated by the target UE carries a pseudonym indication. If therequest for location carries a pseudonym indication, go to Step 306; ifit carries no pseudonym indication, go to Step 308.

In addition, when the LCS system makes a determination that the requestfor location originated by the target UE includes a pseudonymindication, in Steps 306-307, the LCS system may alternatively notassign the target UE a pseudonym that can identify the target UE.Instead, it may send the requestor only the location information of thetarget UE with neither the pseudonym nor the real identity of the targetUE and then terminate the current MO-LR procedure. In the presentinvention, the LCS system may use another method to determine whetherthe real identity of the target UE should be concealed. The LCS systemmay determine whether the requestor for receiving the target UE'slocation information should analyze the real identity of the target UE,and if not, assign a pseudonym for the target UE, and then send thelocation information and the pseudonym of the target UE to therequestor. Otherwise, send the requestor the real identity and locationinformation of the target UE.

FIG. 4 is the flowchart of another embodiment of the present invention.As shown in FIG. 4, in the present embodiment, the procedure of an MO-LRcarrying a requestor identity comprises the following steps:

Steps 401˜403: The target UE sends a Call Management Service Request (CMService Request) to the RAN, requesting to set up a radio signalingconnection with the network. After receiving the CM Service Request, theRAN forwards the CM Service Request to an MSC/MSC Server. Afterreceiving the CM Service Request, the MSC/MSC Server decides whether thetarget UE has subscribed to an MO-LR service initiated by the target UEaccording to the saved information, if the target UE has not subscribedto an MO-LR service, the MSC/MSC Server will return an LCS MO-LRpositioning Result carrying a value of error cause to the target UE soas to reject the MO-LR service request originated by the target UE; ifthe target UE has subscribed to an MO-LR service, the MSC/MSC Serverwill interact with the target UE to complete the authentication andciphering of the target UE; if the target UE has been authenticated, theMSC/MSC Server will notify the target UE that the initiated CM ServiceRequest is accepted and continue with Step 404. If the target UE hasn'tbeen authenticated, the MSC/MSC Server will notify the target UE thatthe initiated CM Service Request has been rejected.

Steps 404˜405: After being authenticated by the MSC/MSC Server, thetarget UE sends a Location Service Invoke to the MSC/MSC Server,requesting the LCS system to position the target UE. The LocationService Invoke includes a pseudonym set by the target UE and a requestoridentity, which asks the LCS system not to offer the requestor the realidentity of the target UE, but to provide the pseudonym of the target UEfor the requestor as providing the requestor with the target UE'slocation information. The Location Service Invoke may further carry aGMLC address designated by the target UE, asking the CN to provide therequestor with the location information of the target UE through theGMLC corresponding with the GMLC address. After receiving the LocationService Invoke, the MSC/MSC Server sends the RAN a Location Request forthe target UE.

Step 406˜407: After receiving the Location Request, the RAN positionsthe target UE to acquire the target UE's location estimate. If itsucceeds in positioning the target UE, the RAN will return the MSC/MSCServer a Location Report carrying the target UE's location information.After it receives the Location Report including the target UE's locationinformation, the MSC/MSC Server determines whether the Location ServiceInvoke initiated by the target UE carries a GMLC address, if it carriesan address of a GMLC, continue to decide whether the MSC/MSC Serveritself can access the GMLC directly which is corresponding to the GMLCaddress. If the MSC/MSC Server can access the GMLC directly, it willdirectly send the GMLC a Mobile Application Part (MAP) SubscriberLocation Report carrying the pseudonym and location information of thetarget UE, wherein the interaction between the V-GMLC and the GMLC asshown in the figure, i.e., Step 409 and Step 412, may be skipped. If theMSC/MSC Server can not access the GMLC directly, the MSC/MSC Server willassign a V-GMLC that the MSC/MSC Server itself can directly access, sendthe V-GMLC an MAP Subscriber Location Report of the target UE whichcarries the target UE's pseudonym, the location information of thetarget UE, the requestor identity, and the GMLC address included in theLocation Service Invoke, and continue with Step 408. If the LocationService Invoke originated by the target UE carries no GMLC address, theMSC/MSC Server will assign a V-GMLC that the MSC/MSC Server itself canaccess directly, send the V-GMLC an MAP Subscriber Location Report ofthe target UE which carries the target UE's pseudonym, the locationinformation of the target UE, and the requestor identity, and continuewith Step 408. If the RAN fails to position the target UE, it willreturn the MSC/MSC Server a Location Report including a value of errorcause and go directly to Step 414, i.e., the MSC/MSC Server returns anLCS MO-LR Positioning Result carrying a value of error cause to thetarget UE via RAN.

Step 408: After receiving the MAP Subscriber Location Report of thetarget UE, the V-GMLC determines whether the MAP Subscriber LocationReport carries a GMLC address, and if yes, go to Step 409; otherwise,the V-GMLC decides whether it can access the requestor directly based onthe requestor identity. If the V-GMLC can access the requestor directly,it will send directly the requestor a Location Information of the targetUE which carries the pseudonym and location information of the targetUE, wherein the interaction between the V-GMLC and the GMLC as shown inthe figure, i.e., Step 409 and Step 412, may be skipped. Otherwise, theV-GMLC will assign a GMLC that is able to access the requestor directlyaccording to the requestor identity and continue with Step 409.

Step 409: The V-GMLC sends an MO-LR Location Information of the targetUE to the GMLC according to the GMLC address which includes the targetUE's pseudonym, the location information of the target UE, and therequestor identity.

Step 410: Upon receiving the MO-LR Location Information of the targetUE, the GMLC sends the requestor the Location Information of the targetUE which carries the pseudonym and location information of the target UEbased on the requestor identity.

Steps 411˜414 are basically the same as Steps 209˜212.

Step 415: The target UE releases the occupied resources of the LCSsystem, i.e., releases the CM, MM, RRC Connection with the LCS system,and terminates the current MO-LR procedure of the circuit-switcheddomain.

FIG. 5 is the flowchart of another embodiment of the present invention.As shown in FIG. 5, in the current embodiment, the procedure of an MO-LRcarrying a requestor identity comprises the following steps:

Step 501: The target UE sends a Service Request to a SGSN, requesting toset up a radio signaling connection with the network. After receivingthe Service Request, the SGSN sets up a signaling connection of PacketSwitched (PS) domain with the target UE.

Step 502-503: The target UE sends an LCS MO-LR Invoke to the SGSN viaRAN, requesting the LCS system to position the target UE. The LCS MO-LRInvoke carries a pseudonym indication and a requestor identity, askingthat the LCS system should provide the requestor with the pseudonym forthe target UE assigned by the LCS system rather than the target UE'sreal identity while the LCS system provides the requestor with thelocation information of the target UE. The Location Service Invoke mayfurther carry a GMLC address designated by the target UE, requesting theSGSN to provide the requestor with the location information of thetarget UE via the GMLC corresponding with the GMLC address. After itreceives the LCS MO-LR Invoke, the SGSN sends the RAN a Location Requestfor the target UE.

Step 504˜505: After receiving the Location Request, the RAN positionsthe target UE and obtains the target UE's location estimate. If itsucceeds in positioning the target UE, the RAN will return the SGSN aLocation Report including the location information of the target UE.After receiving the Location Report, the SGSN decides whether the LCSMO-LR Invoke initiated by the target UE carries a GMLC address GMLCaddress, if it carries a GMLC address, the SGSN will continue to decidewhether the SGSN itself can access the GMLC directly which iscorresponding with the GMLC address. If it can access the GMLC directly,the SGSN will send a Subscriber Location Report to the GMLC directlywhich carries a pseudonym indication, the target UE's real identity, andthe location information of the target UE, wherein the interactionbetween the V-GMLC and the GMLC as shown in the figure, i.e., Step 507and Step 510, may be skipped. Otherwise, the SGSN will assign a directlyaccessible V-GMLC, send the V-GMLC a Subscriber Location Report of thetarget UE carrying the pseudonym indication, the real identity andlocation information of the target UE, the requestor identity, and theGMLC address included in the LCS MO-LR Invoke, and continue with Step506. If the LCS MO-LR Invoke initiated by the target UE carries no GMLCaddress, the SGSN will assign a V-GMLC that the SGSN can accessdirectly, send a Subscriber Location Report of the target UE to theV-GMLC which carries the target UE's pseudonym indication, the realidentity and location information of the target UE, and the requestoridentity, and continue with Step 506. If the RAN fails to position thetarget UE, it will return the SGSN a location report including a valueof error cause and go straight to Step 512, i.e., the SGSN returns thetarget UE a Service Response carrying a value of error cause via RAN.

Step 506: Upon receiving the Subscriber Location Report of the targetUE, based on the pseudonym indication and the target UE's real identitycarried in the Subscriber Location Report, the V-GMLC decides whetherthe V-GMLC itself can assign a pseudonym for the target UE, and if itcan assign the pseudonym, the V-GMLC will assign a pseudonym for thetarget UE according to the real identity of the target UE and continuewith the subsequent procedure; if the V-GMLC can not assign a pseudonymfor the target UE, the V-GMLC may interact with the HLR/HSS of thetarget UE to acquire the address of the target UE's H-GMLC and send theH-GMLC an MO-LR Location Information which carries a pseudonymindication and the real identity of the target UE, requesting the H-GMLCto assign a pseudonym for the target UE. After receiving the MO-LRLocation Information, the H-GMLC assigns a pseudonym for the target UEaccording to the real identity thereof, or interacts with the PMD torequest the PMD to assign a pseudonym for the target UE. Then, theH-GMLC returns the V-GMLC an MO-LR Location Information Ack whichcarries the pseudonym assigned for the target UE.

After acquiring the pseudonym of the target UE, the V-GMLC decideswhether the received message contains the address of the GMLC, and if itcontains the address, go to Step 507; if not, the V-GMLC continues todecide whether the requestor can be accessed directly according to therequestor identity. If the requestor can be accessed directly, theV-GMLC will send a Subscriber Location Report of target UE directly tothe requestor which carries the pseudonym and location information ofthe target UE, wherein the interaction between the V-GMLC and the GMLCas shown in the figure, i.e., Step 507 and Step 510, may be skipped.Otherwise, the V-GMLC will assign a GMLC that can access the requestoraccording to the requestor identity and continue with Step 507.

Step 507: According to the GMLC address, the V-GMLC sends the GMLC theMO-LR Location Information of the target UE which includes the pseudonymand location information of the target UE and the requestor identity.

Step 508: After it receives the MO-LR Location Information of the targetUE, the GMLC sends the requestor the target UE's Location Informationincluding the pseudonym and location information of the target UEaccording to the requestor identity.

Steps 509˜512 are basically the same as Steps 209˜212.

In the above Step 506, the pseudonym of the target UE is assigned by theV-GMLC itself, or is obtained by the V-GMLC which requests the targetUE's H-GMLC/PMD to assign the pseudonym. Alternatively, the V-GMLC maymake no process of the target UE's pseudonym indication, instead, maysend directly the MO-LR Location Information of the target UE to theGMLC which carries the pseudonym indication, the location information ofthe target UE and the requestor identity. Then, the GMLC will assign apseudonym for the target UE according to the pseudonym indication andthe target UE's real identity, or will possibly request the H-GMLC/PMDof the target UE to assign a pseudonym for the target UE and then sendthe requestor the Location Information of the target UE carrying thepseudonym and the target UE's location information.

In addition, it is mentioned in Steps 504˜505 that, if the SGSN canaccess the GMLC, it will directly send a Subscriber Location Report ofthe target UE to the GMLC which includes the pseudonym indication, thereal identity, and the location information of the target UE. In thiscase, after receiving the Subscriber Location Report of the target UE,the GMLC may also assign a pseudonym for the target UE according to thepseudonym indication and the target UE's real identity or may requestthe H-GMLC/PMD of the target UE to assign a pseudonym for the target UE,and then, the GMLC will send the requestor the Location Information ofthe target UE which carries the pseudonym and location information ofthe target UE.

In the second embodiment, the V-GMLC sends the MO-LR LocationInformation to the H-GMLC directly which carries the pseudonymindication and real identity of the target UE, requesting the H-GMLC toassign a pseudonym for the target UE, and then, the H-GMLC returns anMO-LR Location Information Ack to the V-GMLC which includes thepseudonym for the target UE assigned by the H-GMLC. Alternatively, theV-GMLC may send the H-GMLC the MO-LR Location Information which carriesthe pseudonym indication, the real identity and location information ofthe target UE, the requestor identity, and the possible GMLC address.Upon completing assigning a pseudonym for the target UE, the H-GMLCdetermines whether the MO-LR Location Information carries a GMLCaddress. If it carries the GMLC address, according to the GMLC address,the H-GMLC will send the GMLC the MO-LR Location Information includingthe target UE's pseudonym, the location information of the target UE,and the requestor identity. If the MO-LR Location Information carries noGMLC address, the H-GMLC will determine whether it is able to access therequestor immediately based on the requestor identity. If the H-GMLC isable to access the requestor immediately, it will send an MO-LR LocationInformation to the requestor which includes the pseudonym and locationinformation of the target UE; otherwise, according to the requestoridentity, the H-GMLC will assign the address of the accessible GMLC, andthen send the GMLC an MO-LR Location Information carrying the targetUE's pseudonym, the location information of the target UE, and therequestor identity. At last, the GMLC will send an MO-LR LocationInformation to the requestor which includes the pseudonym and locationinformation of the target UE.

In the above embodiments, the pseudonym may be assigned by an H-GMLC, aV-GLMC, or a GMLC which can access the requestor in the LCS system.Alternatively, the pseudonym may be assigned by a H-GMLC, a V-GLMC, anentity of the LCS system, or a GMLC which can access the requestor afterthe H-GMLC, the V-GLMC, the entity of the LCS system, or the GMLCinteracts with an entity of the LCS system. Here, the entity of the LCSsystem may be a PMD or H-GMLC.

In addition, in accordance with the above embodiments, it is efficientlyrealizable for network operators to protect the privacy of thesubscriber's using of the service. The operator of the target UE's homenetwork may sign an agreement with the visited network's operator of thetarget UE. The agreement requires that after the visited network of thetarget UE receives a request for location initiated by the target UEwhich is for asking the network to provide a requestor with the locationinformation of the target UE, whereafter the visited network acquiresthe location information of the target UE. The V-GMLC should not send anMO-LR Location Information of the target UE directly to the GMLC thatcan access the requestor; instead, it should send the MO-LR LocationInformation of the target UE to the H-GMLC which carries the GMLCaddress. Next, the H-GMLC should subsequently assign a pseudonym for thetarget UE, and at last send the requestor the pseudonym and locationinformation of the target UE via the GMLC. In this way, the realidentity of the target UE is hidden and the security of using theservice is improved.

In the case of the target UE asking the LCS system to assign a pseudonymfor the target UE itself, the LCS system may assign a pseudonym that isone-to-one corresponding to a real identity of the target UE based onthe pre-stored information, e.g., the LCS system may assign a pseudonymthat is acquired by enciphering a real identity of the target UE, andthe target UE may register a corresponding service at a requestor withthe pseudonym that is one-to-one corresponding to the target UE's realidentity so as to hide the real identity thereof. Alternatively, inpractical applications, it is possible that the requestor need not torecognize the pseudonym of the target UE upon receiving the target UE'spseudonym and location information. Thus the LCS system may assign apseudonym randomly, that is, there is no fixed relationship ofcorrespondence between the target UE and the pseudonym thereof. Forexample, the target UE may initiate a request for location, asking theLCS system to return the location information of the target UE in anelectronic map format or a format of text. After positioning the targetUE and acquiring the location estimate thereof, the LCS system maydetermine a requestor which has the ability of transforming any formatinto a format of electronic map or text said above based on the savedinformation of requestors' capabilities, and then send the pseudonym andlocation information of the target UE to the requestor. In this case, itis not needed for the requestor to decide whether the target UE hassubscribed to the service according to the pseudonym of the target UE,so it will not be necessary for the requestor to recognize the pseudonymof the target UE. The requestor will directly convert the locationinformation of the target UE according to the requirement, and thenreturn the converted location information of the target UE to the LCSsystem. The LCS system will send the target UE the location informationin an appropriate format of electronic map or text by means of ShortMessage Service (SMS), Multimedia Message Service (MMS), etc. Inaddition, in case that it is not needed for the requestor to make aprocess such as authenticating the user's identity included in thereceived location information of the target UE, the LCS system may notprovide any identity of the target UE according to the pseudonymindication, but send the target UE's location information directly tothe requestor.

To sum up, the foregoing is only preferred embodiments of the presentinvention and should not be construed as limiting the protection scopethereof.

1. A method for processing requests for location, the method comprises:a location service (LCS) system receiving a request for location from atarget user's equipment (UE), and to being requested to provide arequestor with the location information of the target UE; the LCS systempositioning the target UE and obtaining the location information of thetarget UE; and the LCS system determining whether the real identity ofthe target UE should be concealed by (a) determining whether the requestfor location sent by the target UE carries a pseudonym designated by thetarget UE, if yes, sending the location information and a pseudonym ofthe target UE to the requestor; and (b) otherwise, send the requestorthe real identity and location information of the target UE.
 2. Themethod according to claim 1, wherein the step of sending the locationinformation and a pseudonym of the target UE to the requestor comprisesthe steps of: c1. On receiving the location information of the target UEacquired by the Radio Access Network (RAN), the Core Network (CN) in theLCS system deciding whether a GMLC address is carried in the request forlocation initiated by the target UE, if yes, performing Step c2;otherwise, performing Step c3; c2. the CN sending a location report ofthe target UE to a GMLC according to the GMLC address which at leastincludes the location information of the target UE, the GMLC sending alocation report of the target UE to the requestor which at leastincludes the location information and pseudonym of the target UE, andthe current process of the method being terminated; c3. the CN sending alocation report of the target UE to a V-GMLC which at least includes thelocation information of the target UE, and the V-GMLC sending a locationreport to the requestor which at least includes the location informationand pseudonym of the target UE.
 3. The method according to claim 2, inStep c2, before the CN sending the location report of the target UE tothe GMLC, further comprising: the CN deciding whether the GMLC can beaccessed directly according to the GMLC address, if yes, sendingdirectly the location report of the target UE to the GMLC; otherwise,the CN sending the location report of the target UE to the V-GMLC, andthe V-GMLC sending the location report of the target UE to the GMLC. 4.The method according to claim 2, wherein the request for locationfurther comprises a requestor identity.
 5. The method according to claim4, before the V-GMLC sending the location report of the target UE to therequestor, further comprising: deciding whether the requestor can bedirectly accessed according to the requestor identity, if yes, theV-GMLC sending the location report of the target UE to the requestordirectly; otherwise, sending the location report of the target UE to aGMLC which is adapted to access the requestor, and the location reportof the target UE being sent to the said requestor by the GMLC.
 6. Themethod according to claim 2, wherein the location report further carriesa pseudonym designated by the target UE, or a pseudonym indication. 7.The method according to claim 2, wherein the location report of thetarget UE is an MO-LR Location Information sent to the GMLC, or a MobileApplication Part (MAP) Subscriber Location Report or a SubscriberLocation Report sent to the V-GMLC, or a Location Information sent tothe requestor.
 8. The method according to claim 1, wherein the step ofsending the location information and a pseudonym of the target UE to therequestor comprises: after receiving the location information of thetarget UE acquired by the RAN, the CN in the LCS system sending alocation report of the target UE to a V-GMLC which at least carries thelocation information of the target UE, the V-GMLC sending the locationreport of the target UE to a H-GMLC, and the H-GMLC sending therequestor a location report of the target UE which at least includes thelocation information and pseudonym of the target UE.
 9. The methodaccording to claim 8, wherein the step of sending the requestor thelocation report of the target UE by the said H-GMLC comprises: theH-GMLC determining whether a GMLC address is carried in the locationreport of the target UE, if yes, the H-GMLC sending the location reportof the target UE to a GMLC which corresponds to the GMLC address, andthe said GMLC sending the requestor the location report of the targetUE; otherwise, according to the requestor identity, the H-GMLC furtherdeciding whether the requestor can be accessed directly; if therequestor can be accessed directly, the H-GMLC sending directly thelocation report of the target UE to the requestor; if the requestor cannot be accessed directly, the H-GMLC sending the location report of thetarget UE to a GMLC that can is adapted to access the requestor, and theGMLC sending the said requestor the location report of the target UE.10. The method according to claim 8, before the H-GMLC sending thelocation report of the target UE to the requestor, further comprising:the H-GMLC deciding whether the requestor can be accessed directlyaccording to the requestor identity, if yes, sending directly therequestor the location report of the target UE; otherwise, sending thelocation report of the target UE to a GMLC that is adapted to access therequestor, and the GMLC sending the said requestor the location reportof the target UE.
 11. The method according to claim 8, wherein thelocation report of the target UE further carries a pseudonym designatedby the target UE or a pseudonym indication.
 12. The method according toclaim 1, in the step of sending the location information and a pseudonymof the target UE to the requestor, after the LCS system sending therequestor the location information and pseudonym of the target UE,further comprising: the requestor processing the received locationinformation of the target UE and returning the processing result of thetarget UE's location information to the LCS system, and the LCS systemreturning the target UE the processing result of the target UE'slocation information.
 13. The method according to claim 1, wherein therequest for location originated by the target UE is a Location ServiceInvoke sent to a Mobile services Switching Centre (MSC)/MSC Server inthe CN or an LCS Mobile Originating Location Request (MO-LR) Invoke sentto a Serving General Packet Radio Service Support Node (SGSN) in the CN;the said requestor is an LCS Client, a group of LCS Clients, or thetarget UE itself.
 14. A method for processing requests for location, themethod comprises: a location service (LCS) system receiving a requestfor location from a target user's equipment (UE), and to being requestedto provide a requestor with the location information of the target UE;the LCS system positioning the target UE and obtaining the locationinformation of the target UE; and the LCS system determining whether thereal identity of the target UE should be concealed by (a) determiningwhether the request for location sent by the target UE carries apseudonym indication, if yes, assigning a pseudonym for the target UE,and then sending the location information and pseudonym of the target UEto the requestor; and (b) otherwise, sending the requestor the realidentity and location information of the target UE.
 15. The methodaccording to claim 14, wherein the pseudonym is assigned by a HomeGateway Mobile Location Centre (H-GMLC), a Visited Gateway MobileLocation Centre (V-GLMC), or a Gateway Mobile Location Centre GMLC whichis adapted to access the requestor in the LCS system; alternatively, thesaid pseudonym is assigned by a H-GMLC, a V-GLMC, an entity of the LCSsystem, or a GMLC which is adapted to access the requestor after theH-GMLC, the V-GLMC, the entity of the LCS system, or the GMLC interactswith an entity of the LCS system; the said entity of the LCS system is aPseudonym Mediation Device (PMD) or H-GMLC.
 16. A method for processingrequests for location, the method comprises: a location service (LCS)system receiving a request for location from a target user's equipment(UE), and to being requested to provide a requestor with the locationinformation of the target UE; the LCS system positioning the target UEand obtaining the location information of the target UE; and the LCSsystem determining whether the real identity of the target UE should beconcealed by (a) determining whether the request for location sent bythe target UE carries a pseudonym designated by the target UE, if yes,sending the location information and pseudonym of the target UE to therequestor; and (b) otherwise, further deciding whether the request forlocation sent by the target UE carries a pseudonym indication; if therequest for location carries a pseudonym indication, assigning apseudonym for the target UE, and then sending the location informationand pseudonym of the target UE to the requestor; if the request forlocation carries no pseudonym indication, sending the requestor the realidentity and location information of the target UE.
 17. The methodaccording to claim 16, wherein the pseudonym is assigned by a HomeGateway Mobile Location Centre (H-GMLC), a Visited Gateway MobileLocation Centre (V-GLMC), or a Gateway Mobile Location Centre GMLC whichis adapted to access the requestor in the LCS system; alternatively, thesaid pseudonym is assigned by a H-GMLC, a V-GLMC, an entity of the LCSsystem, or a GMLC which is adapted to access the requestor after theH-GMLC, the V-GLMC, the entity of the LCS system, or the GMLC interactswith an entity of the LCS system; the said entity of the LCS system is aPseudonym Mediation Device (PMD) or H-GMLC.
 18. A method for processingrequests for location, the method comprises: a location service (LCS)system receiving a request for location from a target user's equipment(UE), and to being requested to provide a requestor with the locationinformation of the target UE; the LCS system positioning the target UEand obtaining the location information of the target UE; and the LCSsystem determining whether the real identity of the target UE should beconcealed by determining whether the request for location sent by thetarget UE carries a pseudonym indication, if the request for locationcarries a pseudonym indication, assigning a pseudonym for the target UE,and then sending the location information and pseudonym of the target UEto the requestor; if the request for location carries no pseudonymindication, further deciding whether the request for location sent bythe target UE carries a pseudonym designated by the target UE; if therequest for location carries a pseudonym, sending the locationinformation and pseudonym of the target UE to the requestor; if therequest for location carries no pseudonym, sending the real identity andlocation information of the target UE to the requestor.
 19. The methodaccording to claim 18, wherein the pseudonym is assigned by a HomeGateway Mobile Location Centre (H-GMLC), a Visited Gateway MobileLocation Centre (V-GLMC), or a Gateway Mobile Location Centre GMLC whichis adapted to access the requestor in the LCS system; alternatively, thesaid pseudonym is assigned by a H-GMLC, a V-GLMC, an entity of the LCSsystem, or a GMLC which is adapted to access the requestor after theH-GMLC, the V-GLMC, the entity of the LCS system, or the GMLC interactswith an entity of the LCS system; the said entity of the LCS system is aPseudonym Mediation Device (PMD) or H-GMLC.
 20. A method for processingrequests for location, the method comprises: a location service (LCS)system receiving a request for location from a target user's equipment(UE), and to being requested to provide a requestor with the locationinformation of the target UE; the LCS system positioning the target UEand obtaining the location information of the target UE; and the LCSsystem determining whether the real identity of the target UE should beconcealed by determining whether the requestor for receiving the targetUE's location information should analyze the real identity of the targetUE, if no, assigning a pseudonym for the target UE, and then sending thelocation information and the pseudonym of the target UE to therequestor; otherwise, sending the requestor the real identity andlocation information of the target UE.